fix: provision dependency-only directories safely - #242

== tests/fm-spawn-provision.test.sh ==
ok - a worktree declaring no recognized manifest provisions nothing and succeeds
ok - a bare requirements.txt installs only its dependencies
ok - bare requirements take precedence over a standalone uv.lock
ok - a standalone uv.lock installs only its locked dependencies
ok - an unresolved standalone uv.lock records a capability gap without refusing
ok - a path-dependent standalone uv.lock records a capability gap
ok - an npm lock without its required manifest records a capability gap
ok - a pnpm lock without its required manifest records a capability gap
ok - provisioning installs once and reuses an unchanged worktree without install cost
ok - a changed dependency manifest invalidates the cache
ok - installer configuration that changes what is installed invalidates the cache
ok - a fingerprint match with a broken environment is a miss, not a hit
ok - Node installs include declared validation dependencies deterministically
ok - an environment whose recorded runtime no longer matches is reprovisioned
ok - pip directives and includes are parsed, so an unchanged component stays cached
ok - build output written inside node_modules does not invalidate a healthy cache
ok - a declared manifest that cannot be read refuses instead of hashing to nothing
ok - a component nested past the scan depth is reported everywhere, not dropped
ok - a dependency scan that outlives its bound warns, reports, and launches unprovisioned
ok - a uv pip check that could not run is recorded as unverified, never as a verdict
ok - a python project with no committed lock or requirements file is named, not silently skipped
ok - the pyproject declaration read is bounded and degrades to undetermined
ok - a pyproject.toml holding only tool configuration provisions nothing and reports nothing
ok - a reported metadata inconsistency is recorded and launches; an unusable environment still refuses
ok - a failing install refuses the spawn and records no fingerprint
ok - an install that hangs is bounded and refuses instead of wedging the spawn
ok - a signal-killed bounded install is reported as a failure
ok - empty, zero, and nonnumeric provisioning tunables refuse before detection
ok - a traversal failure is distinct from a successful undeclared-worktree no-op
ok - a directory name containing another as a token is not deduped away
ok - a bounded call to a command that cannot be executed is a failure
ok - an environment signature that captures nothing refuses instead of hashing nothing
ok - a host without python3 warns and launches unprovisioned rather than refusing
ok - a host with no bounding mechanism runs nothing and launches unprovisioned
ok - a python project with no uv is left unprovisioned and reported, not refused
ok - a recognized but unsupported package manager is a recorded gap, not a refusal
ok - a worktree over the component budget provisions what it can and reports what it skipped
ok - the component budget is spent on what the task names before detection order
ok - a host capability gap is reported to the lane, not only to the operator
ok - a symlink planted at the report path is replaced rather than written through
ok - a requirements graph past the traversal cap is a gap, never a fingerprint over a prefix
ok - the JS package manager comes from what the project declares, not from lockfile precedence
ok - detection is driven by what the worktree declares and skips installed trees
ok - a uv workspace syncs every member while a single project keeps the plain sync
ok - uv workspace member manifests participate in the cache fingerprint
ok - a Node pin is read from what the project declares, and only when unambiguous
ok - a declared Node runtime that cannot be found leaves the JS components unprovisioned
ok - a declared Node runtime is resolved to its highest installed match and exported for the lane
ok - a Node pin wins for the Node toolchain and changes resolution for nothing else
ok - a shared pinned Node prefix is published once and never rebuilt under a running lane
ok - concurrent publishes each return a complete prefix and never nest one inside the other
ok - a published prefix that stops validating is stepped over, leaving the stale one untouched
ok - a spawn provisions its worktree after verification and before endpoint creation
ok - provisioning failure refuses the spawn instead of launching a lane that cannot validate
ok - a worktree over the component budget launches, warns, and records what it skipped
ok - the crewmate can read, inside its own worktree, what provisioning skipped and why
ok - teardown removes the provisioning log with the rest of the per-task state
ok - a later provisioning failure leaves the worktree clean without writing to the main clone
ok - an unignored install directory refuses before any installer runs, and never writes to the main clone
ok - provisioning is opt-out per spawn and per home, and the choice is recorded
ok - a lease that provisions nothing clears the previous task's report instead of inheriting it
ok - an unparseable provisioning setting refuses rather than silently disabling the gate
ok - a project declaring no recognized manifest spawns exactly as before
# all fm-spawn-provision tests passed

== tests/fm-herdr-lab.test.sh ==
ok - fm-herdr-lab: names fail closed and require the lab prefix
ok - fm-herdr-lab: provision timeout is configurable only within a bounded range
ok - fm-herdr-lab: provisioning, scoped calls, guarded teardown, and fleet tripwire are deterministic
ok - fm-herdr-lab: missing tripwire refuses teardown before any Herdr call
ok - fm-herdr-lab: agent argv routing inserts only the owned session before --
ok - fm-herdr-lab: changed default fleet state is a hard failure
ok - fm-herdr-lab: unrelated same-operator fleet churn is audited without blocking teardown
ok - fm-herdr-lab: lab-attributed default fleet drift retains teardown refusal
ok - fm-herdr-lab: transient default runtime activity does not change fleet identity
ok - fm-herdr-lab: provisioning requires a proven-running default session
ok - fm-herdr-lab: default running proof requires the JSON Boolean true
ok - fm-herdr-lab: destructive lab boundaries re-prove the running default session
ok - fm-herdr-lab: an owned stopped lab can re-provision safely
ok - fm-herdr-lab: failed deletion retains ownership until absence is confirmed
ok - fm-herdr-lab: timed-out provisioning cancels the launch before teardown

== tests/fm-backend-autodetect-smoke.test.sh ==
ok - real herdr: fm-spawn.sh auto-detects herdr from HERDR_ENV=1 (no explicit config) and prints the loud notice
ok - real herdr: auto-detected spawn records backend=herdr and herdr_session/workspace/tab/pane fields in meta
ok - real herdr: the auto-detected spawn's launch command actually ran in the herdr pane
ok - real herdr: teardown completes the auto-detected spawn/teardown cycle (meta cleared, pane closed)
== tests/fm-backend-herdr-eventwait-smoke.test.sh ==
ok - real herdr (herdr 0.7.3): events.subscribe capability gate passes (protocol >= 16, events surface present in api schema)
ok - real herdr (herdr 0.7.3): a driven idle->blocked transition returns the blocked record in 0.425s (pane w1:p2)
ok - real herdr: the watcher fast-path enqueues a stale wake naming the task window from the live blocked transition